[Toolkit] Rework kits architecture, change term for "recipe" #2986
+2,514
−2,682
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This big PR modify the kits architecture from Toolkit, I get a lot of inspiration from Symfony Recipes and I think we are on something really really good.
The actual architecture was too coupled to a Symfony application structure, which made things easy for the website but not for working on "Recipes" (previously known as Components").
Before:
after:
Now, everything under
kits/*/
is a recipe. There is noAsset\Component
norAsset\StimulusController
anymore, everything was simplified a lot.A Recipe:
manifest.json
file, for describing its name, description, some dependencies (either PHP packages or other Recipes, which files to copy (and where), its type (either acomponent
, or something else in the future), etc...EXAMPLES.md
file, it's mainly internal for the WebsiteThe CLI still works as expected:
Enregistrement.de.l.ecran.2025-08-11.a.00.47.53.mov
The website too:
Enregistrement.de.l.ecran.2025-08-11.a.00.49.47.mov